home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
echo311.zip
/
FIXED.DOC
< prev
next >
Wrap
Text File
|
1992-03-23
|
9KB
|
177 lines
EchoDor will now do a Confirm on [S]ave.
^A, SEEN-BY, and PATH lines were getting wrapped when using a MAXLINELENGTH
command. This has been corrected; however, ^A, SEEN-BY, and PATH lines will
always be displayed as full 72 character lines.
A problem was found in EchoNLCP causing it to skip nodes (yep, I finally
found a problem). This has hopefully corrected the problem.
Corrected a problem in EDorPurg that caused it to lose the high message
pointer in message #1 in echo areas.
Main menu can now do area "select". This includes changing areas by number,
and special commands <, +, -, >. You can not "select" an area by name from
the main menu, to select by name you must still use the [A] or [J] command.
Comment area will now default to "PRIVATE" if the area allows private message
entry. To enable private messages in the comment area, set the "P" flag in
the AreaDesc table to Y.
Hopefully the problem with ^Z and ^A not working in the visual editor from
the remote end had been fixed.
EchoDor now does NOT include SOFT CR's (0x8d) in the message by default. If
you want EchoDor to include SOFT CR's in the message, add USESOFTCR to the
EchoDor.Ctl file.
Hot keys didn't work on the help prompt.
A request was made to "highlight" the one line menus. This has been done
so that users will have a better idea of what to do.
If you used the "restrict" option in the EchoUser program, it would not
restrict the user you were working on, but would restrict the logged on
user (the sysop).
EchoUser has new options. These include "Global restrict" and "Clear Message
area". Read the documentation for an explination of these options.
The "Command string" area was origionally limited to 40 characters. This has
been expanded to 80 characters. This will allow you to put more information
into the command string.
New EchoDor control option, VisualEsc. This allows you to define characters
(such as period (.) or slash (/)) which when typed in column 1 on the visual
screen, will act the same as an esc. Makes Visual editor even easer to use.
If you want to use this add a line something like:
VISUALESC ./\
to the EchoDor.Ctl file. The three characters, period (.), slash (/) and
back slash (\) will if typed in column 1 act exactly was if the user pressed
the ESC key.
I have separated the [I]gnore sections for packing mail and for reading
messages. This will allow a user to have one setup for reading mail and
one setup for packing mail. For example, let's say there is a local echo
that the user reads and the traffic is small. The user can put that echo
in the [I]gnore option from the [U]ser setup menu. Then the user can go
to the [P]ack section and [I]gnore all ares except what he wants to pack
if he selects the Pack All Areas option.
The [I]gnore system can now except multiple numbers on the Activate area
and the Ignore area prompts. Multiple numbers are separated by spaces.
Removed the NOTIME parameter from the EchoDor.Ctl file. This parameter is
now available in the DoorDriv.Ctl file.
The registration of EchoDor is now controlled by a KEY file. If this file
is not present, EchoDor will beep and display the "Not registered" screen.
I have done this to make it easer for registered users to upgrade. Once
the EchoDor.Key file is in place, you won't have to get a new copy from
me ... just copy the stuff into the directory and it will work registered.
Fixed a minor problem which would sometimes cause EchoDor to exit with an
error 005 if a user went into echodor then immediately exited.
Fixed the HCopy problem which would cause EchoDor to "lock up" if HCopy was
selected and you didn't have a printer attached to the computer or some
printer problem occured. EchoDor now writes to the printer using BIOS calls
and can detect if the printer goes off line or malfunctions.
I've reduced the memory requirements of EchoDor by using Overlays. I have
structured the overlays so that you should not see any loss of operating
speed. The current memory requirements of EchoDor is now 303k. Warning:
don't try to compress EchoDor with LZEXE or PKLite. It probally won't work!!!
Fixed a problem which caused EchoDor to not go online when the sysop used
the DOOR.SYS (WC3.0 or GAP) drop file.
Improved the carrier detection scheme used in EchoDor. In older versions
if the user was displaying a large screen and the fossil didn't have enough
buffer to hold the entire file and the user dropped carrier, EchoDor would
hang. This has hopefully been corrected.
There was a problem when specifying a starting message number when packing
or scanning mail. EchoDor would always start on the message following the
specified number. This problem has been corrected.
EchoDor can now swap itself out of memory when it does a "shell to dos". To
enable this feature add the parameter "SWAPFILENAME" to the DOORDRIV.CTL file.
Be sure to read the documentaton on this feature before you use it. If
swapping is enabled, memory requirements for EchoDor when you drop to DOS is
about 15k.
It has been requested to allow the SYSOP to configure the chat colors used.
Two new parameters in the DOORDRIV.CTL file will now allow you to configure
the colors used for chat. These are CHATUSERCOLOR and CHATSYSOPCOLOR.
EchoDor can now be told to reconize the GT embedded message codes. These
are ^E (pause then non-stop), ^R (non-stop), ^T (disable abort). The ^T
actually produces no action within EchoDor. To "turn on" this feature put
a G in the "P" column of the area table. The P column is becomming more
the type of messages allowed and less just a "private" flag.
EchoDor can now play music if it's embedded in the message. This will be
most useful when using GT messages.
It appears that some LANs have problem when files are opened in compability
mode on the network. I have made changes in EchoDor which will hopefully
improve LAN compability.
Problems were found using the Alias functions. EchoDor would not ask if the
user wanted to use an alias name during message entry. Also, sometimes when
the alias name was set, problems occured in the user menu.
When displaying a area list from the AreaDesc area (not from a file), the
"More ?" prompt would not allow the user to stop the entry. The "More ?"
prompt has been replaced with a "Continue Y/n ?" prompt which will allow
the user to stop the display.
When specifying areas to be [I]gnored, EchoDor would only allow a maximum
of 10 entries to be specified at one time. Some users were putting in long
lists of area numbers which would cause all entries beyond the 10th entry
to be skipped. This problem has been corrected. EchoDor will now allow as
many entries as the user specifies. I have also added a special entry 'ALL'.
If the user enters ALL, every area will either be ignored or activated de-
pending on which one the user selected.
I found a problem in EDorPurg which would allow it to become confused while
relinking messages. This would be caused by a message that was incorrectly
linked (7 > 10 > 5) or (15 < 20 < 12) or (15 < 15). I have put extra checking
into EDorPurg which will cause it to break out of the link loop should this
type of condition occur.
When EchoDor recorded the number of times read, it would change the date/time
stamp of the message file. This would cause no problem unless you tried to
use the FDAYS option on EDorPurg. EchoDor will now preserve the date/time
stamp of the message file when updating the times read and received bits.
The FDays & MDays options on the EDorPurg prgoram has been fixed.
The [U]ser List option in the User Maintenance routine has been changed to
[L]ist User file. The [U] option is now used for [U]pload Protocol.
EchoDor now allows a user to upload a message. If the proper parameters are
specified in the EchoDor.Ctl file, EchoDor will ask the user if they wist to
upload a message. If they respond "Y", EchoDor will present the protocols
listed in the UPLOADFILE. It will then "switch" to the upload and being the
upload. When the upload is completed, EchoDor will import the message (using
word wrap mode), then switch to the editor so the user can "taylor" the just
uploaded message. The name of the file used for the upload is unimportant
as EchoDor will import the first file it finds in the upload directory.
If a user was running a multiple zone setup, it became necessary to always
insert zone information in every message going out from EchoDor. EchoDor
will now watch for a multiple zone setup, if one is detected, EchoDor will
place an ^AINTL line in every net mail message. This function can also be
forced with a FORCEZONE command in the EchoDor.Ctl file.
There was a problem found in FastLink and EDorPurg which would cause these
programs to reset the file date when relinking the reply thread pointers.
This problem has been corrected in both programs.
There was an initialization problem in both FastLink and EDorPurg which could
cause inpredectable activity in some cases. This has been corrected.